home *** CD-ROM | disk | FTP | other *** search
- Subject: Re: How to solve access exception during part close?
- Sent: 9/17/96 11:28 AM
- Received: 9/17/96 11:28 AM
- From: mlanett@meer.net (Mark Lanett)
- Reply-To: ODF-Interest@CILabs.ORG
- To: OpenDoc Development Framework Discussion List
-
-
- >I'm getting an access exception when I try to close my part (via the
- >window close box). In MacsBug it says: "access exception at somIsObj..."
- >After I issue an "ea" in MacsBug I get a dialog saying: "The file
- >was not found."
-
- Do you get any kind of stack crawl?
-
- >Since the window is instantiated with a plain-old C++ new, rather than
- >an FW_CNew, I don't understand how it gets destructed - but surely it
- >does since samples like ODFForm and ODFDraw do the same thing without
- >crashing.
-
- FW_NEW handles exceptions during object construction (and some related
- stuff). It doesn't make an object garbage-collectable or anything like
- that. Therefore whether something is allocated with FW_NEW or ::new, you
- still have to delete it (there is no FW_DELETE; regular delete suffices for
- both). ODF handles this for window objects.
-
- >Any ideas on how I can solve this?
-
- Some people are distressed that I have to make this suggestion, but I've
- found it to be extremely effective at times: use the debugging build of
- OpenDoc and put the symbol files (on DR5) in the OpenDoc libraries folder,
- and keep them open in the debugger. You'll get stack crawls going back
- through OpenDoc when a crash occurs.
-
-
- --
- Mark Lanett, OpenDoc Framework, Apple Computer